Instance Formatting Metadata

After creating a new .REQ file, the InstanceFormattingMetadata appears with no value by default: no overrides have been indicated for the stylesheet selected.



Users can modify the InstanceFormattingMetadata if a business need exists.  The stylesheet will apply standard formatting.  Enter elements under InstanceFormattingMetadata only if a need exists to override the defaults in the stylesheet. To add override elements, right-click on the InstanceFormattingMetadata element and add the needed elements and their values.



  • InstancePageSize – The default is Letter; however, you can set the value to Legal to create the document for legal size paper or set the number of inches. 
  • InstancePageOrientation – The default is Portrait; however, you can set the value to Landscape to rotate the page orientation..  
  • InstanceBaseFontName – The default is Serif; only change this value if an approved product override or a statutory requirement exists.  The supported overrides are:
    • Sans -  prints the body of the document in Sans Serif font
    • Condensed – prints the body of the document in a condensed font (ex. Arial Narrow)
  • InstanceBaseFontSize - The default is 10pt. Only change this value if an approved product override or a statutory requirement exists.
  • InstanceMinimumBodyFontSize – Certain states require a minimum font size. For example, IL UCC require a 12 point font; the user should set Instance Minimum Body Font Size to 12 and Instance Base Font Size to 12.
  • InstanceMinimumTaglineFontSize – For recordable documents, several states that in addition to having a requirement for the body font size also require the tagline to be a minimum font size.  The requirement is typically 10pt for the override.
  • BodyTextBaselineToBaselineHeight – It is sometimes necessary to modify the spacing between lines of text slightly to fit all necessary text on the first page or to avoid having a last page with only a few lines of text.  The default value is always one (1) pt larger than the base font size (ex. 11pt on our standard 10pt documents).  If implementing an override, reduce this number by .5 pt (ex. 10.5pt on our standard 10pt documents).  Additional reduction will cause text to begin overlapping.  This value should be profiled if only required for certain instances (ex. governing jurisdictions) of the document.
  • ParagraphSpacingPoints – Similar to BodyTextBaselineToBaselineHeight, use this option to modify spacing in the document.  This option modifies the setting for the spacing between paragraphs and sections.  The default value is 3pt; it is suggested that the override should be at least 1pt to maintain some spacing between paras and sections.  This value should be profiled if only required for certain instances (ex. governing jurisdictions) of the document.
  • SectionNumbering – Use this option to specify if only certain governing jurisdictions of the EPM content require section numbering.  This occurs with the NJ Motor Vehicle Lease agreement.
  • Margins  - The following example displays the available elements for children of Margins:


    • For all of the InstanceXXX elements (highlighted in yellow above) the default for this value varies depending on the stylesheet used.  For non-recordable content the default is 0.5in; for recordable content the default is 0.6in.  Modify this only if a statutory requirement (ie. recordable document) exists.  For recordable documents, use the common file to maintain consistency across documents. The common file uses both the top margin value and a table with a RowHeight attribute to meet the overall top margin requirements. 
    • The last page’s margins cannot be larger than any middle page margins.
      Note: Rider documents should always have its margins set to the ‘last page margin’ requirements
  • TableCellBackgroundColor – Use this value to determine the color or shading used for those table cells with the BackgroundColor attribute set to MetadataValue.  This allows the user to make the change in one place vs changing it at each table cell.  The supported values are:
    • Black
    • Gray
    • LightGray
    • User defined value – If the color needed is not listed as a standard option the user can enter an RGB color in the following format (rgb must be lowercase):   rgb(0,0,0)